Run Workflow Log

By default, whenever you run a successfully deployed Cloudhouse Alchemy Compatibility Package using Cloudhouse.Container.Run.exe, the Run Log Cloudhouse.Run.log is created. The log is created in the same folder as the deployed Compatibility Package, specified by the /deploytype flag on the deployment command line. The log is also output to the console at the same time.

Note: A Compatibility Package has to be deployed before it can be run. The Run Log leverages log4net. Please see their website for further information.

The configuration of the Run log file and its behaviour is controlled via the Cloudhouse.container.run.exe.config configuration file found in the folder the Compatibility Package was deployed to.

Note: The configuration file contains the recommended settings for a Compatibility Package, but you can modify this file to control the behaviour of logging, as detailed in Configuring Logging.

Log Format

The entries in the Cloudhouse.Run.log are formatted as follows:

%Date% %LogLevel% %Component% - %Message%"

Where:

Category

Description

Date

Date and time the log file entry was written.

LogLevel

Defines the type of log entry:

  • INFO – General information about what is happening during each component. For example, Starting service installation.

  • WARNING – Contains information you want to be warned about that could affect the way the Compatibility Package is being run, but which do not cause the run to fail. For example, The service {name} will be run as the LocalSystem account instead of {username}.

  • ERROR – Errors that have stopped the deployment from succeeding.

  • DEBUG – Detailed information of each component and is used to record information on how the Compatibility Package Runtimes are running.

Component

The area the log line relates to. For example, ServicesComponent relates to information about Services.

Message

The message associated with the log line.

For example:

2023-01-10 17:16:48,592 INFO   ServicesComponent - Starting service.

Where:

  • 2023-01-10 17:16:48,592 – is the Date and Time the message was written.

  • INFO – is the log level.

  • ServicesComponent – is the relevant Component.

  • Starting service – is the message.

Note: By default, INFO logs are created during package management. Setting the log level to DEBUG increases the verbosity of the logs and should only be used during troubleshooting.

See the Configuring DEBUG Logging section of Configuring Logging for more information.